Automated user information provision using images

ABSTRACT

A method for automated user information provision using an image includes requesting at least one user information image in response to receiving a user information form from a requesting entity over a network. The at least one user information image is received from a camera. The at least one user information image is analyzed using a processor to determine that the at least one user information image includes requested user information in at least one request section of the user information form. The requested user information is automatically provided into the at least one request section of the user information form. The user information form including the requested user information in the at least one request section is displayed on a display. The user information form may then be sent over the network to provide the requested user information to the requesting entity.

CROSS REFERENCE

This application is a Continuation of U.S. patent application Ser. No.13/117,210 filed on May 27, 2011, entitled “Automated User InformationProvision Using Images,” the disclosure of which is incorporated hereinby reference.

BACKGROUND

Field of the Invention

The present invention generally relates to online and/or mobile paymentsand more particularly to using images to automate the provision of userinformation to a user information form that may be used in making onlineand/or mobile payments.

Related Art

More and more consumers are purchasing items and services overelectronic networks such as, for example, the Internet. Consumersroutinely purchase products and services from merchants and individualsalike. The transactions may take place directly between a conventionalor on-line merchant or retailer and the consumer, and payment istypically made by entering user information such as user financialinformation (e.g., credit card information.) Transactions may also takeplace with the aid of an on-line or mobile payment service provider suchas, for example, PayPal, Inc. of San Jose, Calif. Such payment serviceproviders can make transactions easier and safer for the partiesinvolved. Purchasing with the assistance of a payment service providerfrom the convenience of virtually anywhere using a mobile device is onemain reason why on-line and mobile purchases are growing very quickly.

As mentioned above, online and/or mobile payments typically require thata user provide a variety of user information. For example, users may berequired to sign up for an account with a payment service provider byproviding a name, an address, financial information, and/or a variety ofother information known in the art, in order to make a payment. Inanother example, payments may simply require user to provide a varietyof financial information. Conventionally, users are provided forms inwhich they must manually key in such information using an input deviceon a computer system. The process of manually keying in user informationto forms is time-consuming and error-prone, which can lead to userdissatisfaction.

Thus, there is a need for an improved user information provision system.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a flow chart illustrating an embodiment of a method for theautomated provision of user information using images;

FIG. 2a is a front view illustrating an embodiment of a user informationform displayed on a user device;

FIG. 2b is a front view illustrating an embodiment of the user device ofFIG. 2a displaying selections to manually fill in the user informationform or automatically fill in the user information form using images;

FIG. 2c is a front view illustrating an embodiment of the user device ofFIG. 2a displaying an user information image request screen;

FIG. 2d is a perspective view illustrating an embodiment of a userproviding a user information image to the user device of FIG. 2 a;

FIG. 2e is a front view illustrating an embodiment of a user informationimage provided to the user device of FIG. 2 a;

FIG. 2f is a front view illustrating an embodiment of a user informationimage provided to the user device of FIG. 2 a;

FIG. 2g is a front view illustrating an embodiment of a user informationimage provided to the user device of FIG. 2 a;

FIG. 2h is a front view illustrating an embodiment of the userinformation form of FIG. 2a that has been automatically provided userinformation from the user information images of FIGS. 2e, 2f, and 2g onthe user device of FIG. 2 a;

FIG. 3 is a schematic view illustrating an embodiment of a networkedsystem;

FIG. 4 is a perspective view illustrating an embodiment of a userdevice;

FIG. 5 is a schematic view illustrating an embodiment of a computersystem; and

FIG. 6 is a schematic view illustrating an embodiment of a user device.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

In one embodiment, the present disclosure provides a system and methodfor automatically providing user information to a user information formusing an image of user documentation. A user information form isreceived by a user device over a network from a device of a requestingentity such as a payment service provider device or a payee device. Inresponse to receiving the user information form, the user devicerequests a user information image of user documentation. A user may usea camera on the user device to take the user information image of theuser documentation, and that user information image may then be analyzedby the user device using a variety of techniques including OpticalCharacter Recognition (OCR) to determine whether it includes userinformation requested in request sections of the user information form.If the requested user information is included in the user informationimage, the user device automatically enters the requested userinformation into the request sections of the user information form anddisplays it on a display of the user device. A user may edit and/orconfirm the user information in the request sections of the userinformation form and then send the user information form over thenetwork to the requesting entity device.

Referring now to FIGS. 1, 2 a, 2 b, and 2 c, a method 100 forautomatically providing user information to a user information formusing an image is illustrated. In the embodiment of the method 100described below, a requesting entity is requesting user information fromthe user to open up a payer account, and that requesting entity may be apayment service provider such as, for example, PayPal, Inc. of San Jose,Calif., that assists in the making of payments from the user to a payeeby transferring funds from a user account to a payee account of thepayee. However, the requesting entity may also be a payee requestinguser information from the user to make a payment. These embodiments aremeant to be merely exemplary, and one of skill in the art will recognizethat a variety of modifications may be made to the system discussedbelow without departing from the scope of the present disclosure.

The method 100 begins at block 102 where a user information form isreceived and a user information image is requested. In an embodiment, auser having a user device 200 including a display screen 200 a,illustrated in FIG. 2a , may access a user information form 202 over anetwork (e.g., the Internet) by connecting to a payment service providerdevice of a payment service provider or a payee device of a payee. Inthe illustrated embodiment, the user is attempting to sign up for anaccount with a payment service provider, and the payment serviceprovider is providing the user information form 202, which the userdevice 200 is displaying on the display 200 a, for the user to enteruser information into a plurality of request sections that includes aname request section 204 a, a birth date request section 204 b, aplurality of mailing address request sections 204 c, and a plurality ofpayment information request sections 204 d. However, the illustrateduser information form 202 and request sections 204 a, 204 b, 204 c, and204 d are meant to be merely exemplary, and one of skill in the art willrecognize that a variety of different request sections requestingdifferent user information will fall within the scope of the presentdisclosure. Furthermore, one of skill in the art will recognize that auser information form from a payee or other requesting entity mayinclude the same or similar request sections, and may include differentrequest section without departing from the scope of the presentdisclosure. While the user device 200 is illustrated and described belowas a mobile device such as, for example, a mobile phone or computer, oneof skill in the art will recognize that the automatic providing of userinformation to the user information form using an image may be performedon a desktop computer, on other computing systems connected to anetwork, and/or using a variety of other devices known in the art.

At block 102 of the method 100, the user device 200 may detect thereceipt of the user information form 202 with the plurality of requestsections 204 a, 204 b, 204 c, and 204 d. In one embodiment, the userinformation form 202 may provide metadata to the user device 200 thatdetails the user information being requested in the request sections 204a, 204 b, 204 c, and 204 d. In another embodiment, the user device 200may analyze the user information form 202 to determine what userinformation is being requested. For example, the user device 200 mayanalyze the user information form 202 and determine that the requestsection 204 a is positioned adjacent the word “name” and thus therequest section 204 a is requesting a user name, the request section 204b is positioned adjacent the words “birth date” and thus the requestsection 204 a is requesting a user birth day, etc.

Upon detecting the receipt of the user information form 202, the userdevice 200 requests at least one user information image from the user.For example, as illustrated in FIG. 2b , upon detecting the receipt ofthe user information form 202, the user device 200 may display a manualfill-in option 206 a and an automated fill-in using images option 206 b,and the user may then select the automated fill-in using images option206 b such that the user device 200 displays a user information imagerequest screen 208 on the display 200 a, illustrated in FIG. 2c . Theuser information image request screen 208 includes a plurality of userdocumentation types including a Drivers License documentation type 210a, a Passport documentation type 210 b, a Credit Card documentation type210 c, a Debit Card documentation type 210 d, and a check documentationtype 210 e. While a plurality of user documentation types have beenillustrated, those user documentation types are meant to be merelyexemplary, and one of skill in the art will recognize that a variety ofother user documentation types will fall within the scope of the presentdisclosure. The user information image request screen 208 also includesan image frame 212.

In an embodiment, the user may select one of the user documentationtypes (e.g., the Drivers License documentation type 210 a selected inbold in FIG. 2c ) to indicate the type of documentation the user isgoing to provide an image of. In another embodiment, the user device 200may determine, e.g., from the analysis of the user information form 202and the request sections 204 a, 204 b, 204 c, and 204 d, that an imageof a particular user documentation type should be provided and thatimage may be requested by highlighting the appropriate userdocumentation type (e.g., the Drivers License documentation type 210 ahighlighted in bold in FIG. 2c .) In another embodiment, the userinformation request screen 208 may not display the user documentationtypes.

Referring now to FIGS. 1a, 2d, 2e, 2f, and 2g , the method 100 mayproceed to block 104 where the user device receives a user informationimage. In an embodiment, as illustrated in FIG. 2d , a user 214 may takean image of user documentation 216 using a camera (not illustrated) onthe user device 200 by positioning the user documentation 216 and theuser device 200 such that the user documentation 216 is positioned inthe image frame 212 on the user information image request screen 208, asillustrated in FIG. 2e , and activating the camera. Taking the image ofthe user documentation 216 results in a user information image 216 awhich, in the illustrated embodiment, is a user Drivers License image.The user documentation 216 and the corresponding user information image216 a include a plurality of user information such as, for example, auser name 218 a, a user address 218 b, a user birth date 218 c, and avariety of other user information know in the art. The taking of theuser information image 216 a by the user 214 provides the userinformation image 216 a to the user device 200.

In another embodiment, block 102 of the method 100 may include the userdevice 200 requesting an additional or different image of userdocumentation. For example, in the embodiment illustrated in FIGS. 2fand 2g , either the user has selected one of the user documentationtypes (e.g., the Credit Card documentation type 210 a selected in boldin FIGS. 2f and 2g ) to indicate the type of documentation the user isgoing to provide an image of, or the user device 200 has determined,e.g., from the analysis of the user information form 202 and the requestsections 204 a, 204 b, 204 c, and 204 d, that an image of a particularuser documentation type should be provided and that image has beenrequested by highlighting the appropriate user documentation type (e.g.,the Credit Card documentation type 210 a highlighted in bold in FIGS. 2fand 2g .) The user 214 may then take an image of the front (FIG. 2f )and the back (FIG. 2g ) of the user documentation 216 using a camera(not illustrated) on the user device 200 by positioning the userdocumentation 216 and the user device 200 such that the userdocumentation 216 is positioned in the image frame 212 on the userinformation image request screen 208, and activating the camera. Takingthe images of the user documentation 216 results in a first userinformation image 216 ba (FIG. 2f ) and a second user information image216 bb (FIG. 2g ) which, in the illustrated embodiment, are user CreditCard images. The user documentation 216 and the corresponding userinformation images 216 ba and 216 bb include a plurality of userinformation such as, for example, a user name 220 a, a user credit cardnumber 220 b, a user credit card expiration date 220 c, a user creditcard security code 220 d, and a variety of other user information knowin the art. The taking of the user information images 216 ba and 216 bbby the user 214 provides the user information images 216 ba and 216 bbto the user device 200.

While examples of user documentation 216 and user information images 216a, 216 ba, and 216 bb above include a driver's license and credit card,one of skill in the art will recognize that other user documentationstypes (e.g., the passport documentation type 210 b, debit carddocumentation type 210 d, and check documentation type 210 e) may besubstituted in the system described below without departing from thescope of the present disclosure.

Referring now to FIGS. 1, 2 e, 2 f, and 2 g, the method 100 proceeds toblock 106 where the user information image is analyzed and determined toinclude requested user information. The user device 200 may use avariety of techniques to determine whether the user information image216 includes user information that is requested on the user informationform. In an embodiment, the user device 200 may determine a type of userdocumentation included in the user information image 216. For example,the user device 200 may determine that the user information image 216 aof FIG. 2e includes a drivers license documentation type because it wasreceived in response to a request by the user device 200 for a driverslicense documentation type (e.g., the highlighted Drivers Licensedocumentation type 210 a in bold in FIG. 2c ) or it was receivedfollowing an selection by the user to provide a driver's licensedocumentation type (e.g., the Drivers License documentation type 210 aselected in bold in FIG. 2c .) In another example, the user device 200may use a variety of optical image and character recognition techniquesknown in the art to analyze the user information image 216 a, comparethe user information image to a database of user documentations types,and recognize that the user information image 216 a includes a driver'slicense documentation type.

Furthermore, the user device 200 may determine the state of issue of thedriver's license using a variety of techniques. For example, the userdevice 200 may use a location sensor (not illustrated) included in theuser device 200 to determine the location of the user device 200, anduse that location as the state of issue of the driver's license. Inanother example, in performing optical image and character recognitiontechniques to analyze the user information image 216 a and comparing theuser information image to a database of user documentations types, theuser device 200 may recognize that the user information image 216 aincludes a driver's license documentation type issued in Texas (e.g.,from the word “TEXAS” included in the user information image 216 a, fromthe layout and/or images on the user information image 216 a, and/orfrom a variety of other indicators known in the art.)

The user device 200 may also use optical character recognition (OCR)techniques to analyze the user information image 216 a and detect theuser name 218 a, user address 218 b, and user birth date 218 c includedin the user information image 216 a. In one embodiment, the user device200 may be operable to use only the OCR techniques on the userinformation image 216 a, without the need for the other techniquesdiscussed above, to detect the user name 218 a, user address 218 b, anduser birth date 218 c included in the user information image 216 a.However, in another embodiment, the user device 200 may increase theaccuracy of detecting user information on the user information image 216by using other information retrieved during the method 100 (e.g., userdocumentation type, location of issue of the user documentation type,etc.) to access a database (e.g., over a network) of user documentationtypes to determine what sections of the user information image 216 ainclude particular user information. For example, the user device 200may use the techniques discussed above and determine that the userinformation image 216 a includes a driver's license documentation typethat is issued in Texas. By accessing a database of driver's licenses,the user device 200 may determine that Texas driver's licenses include auser name 218 a located above a user address 218 b, both of which arepositioned in a lower left corner of the driver's license, along with auser birth date 218 c positioned mid-way down the left side of thedriver's license and adjacent the characters “DOB”.

In another embodiment, the user device 200 may determine that the userinformation images 216 ba and 216 bb of FIGS. 2f and 2g include a creditcard documentation type because they were received in response to arequest by the user device 200 for a credit card documentation type(e.g., the highlighted Credit Card documentation type 210 c in bold inFIG. 2c ) or were received following an selection by the of the user toprovide a credit card documentation type (e.g., the Credit Carddocumentation type 210 c selected in bold in FIG. 2c .) In anotherexample, the user device 200 may use a variety of optical image andcharacter recognition techniques known in the art to analyze the userinformation images 216 ba and 216 bb, compare the user information imageto a database of user documentations types, and recognize that the userinformation images 216 ba and 216 bb include a credit card documentationtype.

Furthermore, in performing optical image and character recognitiontechniques to analyze the user information images 216 ba and 216 bb andcomparing the user information images 216 ba and 216 bb to a database ofuser documentations types, the user device 200 may recognize that theuser information images 216 ba and 216 bb includes a credit carddocumentation type issued by a particular credit card company (e.g.,from the word “VISA” included in the user information image 216 ba, fromthe layout and/or images on the user information images 216 ba and 216bb, and/or from a variety of other indicators known in the art.)

The user device 200 may also use optical character recognition (OCR)techniques to analyze the user information images 216 ba and detect theuser name 220 a, credit card number 220 b, and credit card expirationdate 220 c included in the user information image 216 ba, along with thecredit card security code 220 d in the user information image 216 bb. Inone embodiment, the user device 200 may be operable to use only the OCRtechniques on the user information images 216 ba and 216 bb, without theneed for the other techniques discussed above, to detect the user name220 a, credit card number 220 b, credit card expiration date 220 c andcredit card security code 220 d included in the user information images216 ba and 216 bb. However, in another embodiment, the user device 200may increase the accuracy of detecting user information on the userinformation images 216 ba and 216 bb by using other informationretrieved during the method 100 (e.g., user documentation type, issuerof the user documentation type, etc.) to access a database (e.g., over anetwork) of user documentation types to determine what sections of theuser information images 216 ba and 216 bb include particular userinformation. For example, the user device 200 may use the techniques asdiscussed above and determine that the user information images 216 baand 216 bb includes a credit card documentation type that is issued byVisa®. By accessing a database of credit cards, the user device 200 maydetermine that Visa® credit cards (or all credit cards) include a username 220 a positioned in the lower left corner of the front side, acredit card number 220 b positioned across the middle of the front side,a credit card expiration date positioned in the lower right corner ofthe front side, and a credit card security code 220 d positioned in thefar right corner of a box on the back side.

In an embodiment, the user device 200 may determine that the userinformation images 216 a, 216 ba, and 216 bb includes requested userinformation by accessing a memory (not illustrated) in the user device200 to retrieve collaborating user information. For example, the memoryof the user device 200 may include a variety of collaborating userinformation such as, for example, a user name, user birth date, useraddress, user financial information, and/or a variety of other userinformation know in the art. The user device 200 may accesses thiscollaborating information and compare it to the user informationdetected in the user information images 216 a, 216 ba, and 216 bb tohelp to determine if the user information detected in the userinformation images 216 a, 216 ba, and 216 bb is the requested userinformation determined from the user information form 202.

Referring now to FIGS. 1, 2 e, 2 f, 2 g, and 2 h, the method 100proceeds to block 108 where requested user information is automaticallyentered into the user information form and the user information form isdisplayed. As discussed above, the user device 200 analyzes the userinformation form 202 received in block 102 of the method 100 todetermine what user information is being requested in the plurality ofrequest sections 204 a, 204 b, 204 c, and 204 d. The user device 200 maythen determine if the user information detected in the user informationimages 216 a, 216 ba, and 216 bb in block 106 of the method 100corresponds to the user information requested in the user informationform 202 and, if so, automatically enter the appropriate userinformation detected in the user information images 216 a, 216 ba, and216 bb into the request sections 204 a, 204 b, 204 c, and 204 d of theuser information form 202.

For example, the user device 200 may retrieve the user name 218 a and/orthe user name 220 a detected in the user information images 216 a and216 ba and provide a user name (e.g., “Jane Elizabeth Doe”) in the namerequest section 204 a of the user information form 202. The user device200 may also retrieve the user birth date 218 c detected in the userinformation image 216 a and provide a user birth date (e.g.,“03/14/1975”) in the birth date request section 204 b of the userinformation form 202. The user device 200 may also retrieve the useraddress 218 b detected in the user information image 216 a and provide auser address (e.g., “710 Colorado St. 6B, Austin, Tex. 78701”) in theplurality of mailing address request sections 204 c of the userinformation form 202. The user device 200 may also retrieve the creditcard number 220 b, the credit card expiration date 220 c, and creditcard security code 220 d from the user information images 216 ba and 216bb and provide user payment information (e.g., “1234 4567 7890 9876;07/2013; 969”) in the plurality of payment information request sections204 d of the user information form 202.

The user device 200 may then display an account information confirmationscreen 222, illustrated in FIG. 2h , that includes the user informationform 202 with the requested information provided in the request sections204 a, 204 b, 204 c, and 204 d. In an embodiment, the request sections204 a, 204 b, 204 c, and 204 d are editable such that a user may editany of the information provided in the request sections 204 a, 204 b,204 c, and 204 d to correct that user information, if necessary. If oneor more request sections are not filled in, such as if the informationimage(s) does not include all the information requested in the sections,the user may enter the requested information manually, such as by usinga keypad/keyboard or by a copy and paste.

The method 100 then proceeds to block 110 where the user informationform 202 including the requested user information in the requestsections 204 a, 204 b, 204 c, and 204 d is sent to a requesting entity.The user may use the user device 200 to send the user information form202, illustrated in FIG. 2h , over the network to the payment serviceprovider device, the payee device, and/or other requesting entitydevice. In an embodiment, the user device 200 may delete any userinformation images 216 a, 216 ba, and 216 bb provided by the user afterautomatically providing the requested user information into the requestsections 204 a, 204 b, 204 c, and 204 d of the user information form202, and display a notification on the display 200 a of the user device200 that the user information images have been deleted.

Thus, a system and method for automatically providing user informationon a user information form using images has been described that allows auser to quickly and easily provide their information on a form. When auser device of the user detects a user information form, the user devicerequest an image of user documentation. Upon the receipt of such animage, the user device analyzes the image to detect user information andautomatically provides that user information into the appropriateportions of the user information form. Such systems and methods allow auser to automatically provide their information on a form by simplytaking an image of documentation that they already carry around withthem, and saves the time and user effort necessary to manually key thatuser information into the user information form.

Referring now to FIG. 3, an embodiment of a networked system 300 used inthe system described above is illustrated. The networked system 300includes a plurality of user devices 302, a plurality of payee devices304, and a payment service provider device 306 in communication over anetwork 308. Any of the user devices 302 may be the user device 200,discussed above. The payee devices 304 may be the payee devicesdiscussed above and may be operated by the payees discussed above. Thepayment service provider device 306 may be the payment service providerdevice discussed above and may be operated by a payment service providersuch as, for example, PayPal Inc. of San Jose, Calif.

The user devices 302, payee devices 304, and payment service providerdevice 306, may each include one or more processors, memories, and otherappropriate components for executing instructions such as program codeand/or data stored on one or more computer readable mediums to implementthe various applications, data, and steps described herein. For example,such instructions may be stored in one or more computer readable mediumssuch as memories or data storage devices internal and/or external tovarious components of the system 300, and/or accessible over the network308.

The network 308 may be implemented as a single network or a combinationof multiple networks. For example, in various embodiments, the network308 may include the Internet and/or one or more intranets, landlinenetworks, wireless networks, and/or other appropriate types of networks.

The user devices 302 may be implemented using any appropriatecombination of hardware and/or software configured for wired and/orwireless communication over network 308. For example, in one embodiment,a user device 302 may be implemented as a personal computer of a user incommunication with the Internet. In other embodiments, the user device302 may be a smart phone, personal digital assistant (PDA), laptopcomputer, and/or other types of computing devices.

The user device 302 may include one or more browser applications whichmay be used, for example, to provide a convenient interface to permitthe user to browse information available over the network 308. Forexample, in one embodiment, the browser application may be implementedas a web browser configured to view information available over theInternet.

The user device 302 may also include one or more toolbar applicationswhich may be used, for example, to provide user-side processing forperforming desired tasks in response to operations selected by the user.In one embodiment, the toolbar application may display a user interfacein connection with the browser application.

The user device 302 may further include other applications as may bedesired in particular embodiments to provide desired features to theuser device 302. In particular, the other applications may include aautomatic form fill-out application for automatically providing userinformation on a form. The other applications may also include securityapplications for implementing user-side security features, programmaticuser applications for interfacing with appropriate applicationprogramming interfaces (APIs) over the network 308, or other types ofapplications. Email and/or text applications may also be included, whichallow the user to send and receive emails and/or text messages throughthe network 308. The user device 302 includes one or more user and/ordevice identifiers which may be implemented, for example, as operatingsystem registry entries, cookies associated with the browserapplication, identifiers associated with hardware of the user device302, or other appropriate identifiers, such as a phone number. In oneembodiment, the user identifier may be used by the payment serviceprovider device 306 to associate the user with a particular account asfurther described herein.

The payee devices 304 may be maintained, for example, by conventional oron-line merchants, conventional or digital goods sellers, individualsellers, and/or application developers offering various products and/orservices in exchange for payment to be received conventionally or overthe network 308. In this regard, the payee devices 304 may include adatabase identifying available products and/or services (e.g.,collectively referred to as items) which may be made available forviewing and purchase by the user.

The payee devices 304 also includes a checkout application which may beconfigured to facilitate the purchase by the user of items. The checkoutapplication may be configured to accept payment information from theuser through the user device 302 and/or from the payment serviceprovider through the payment service provider device 306 over thenetwork 308.

Referring now to FIG. 4, an embodiment of a user device 400 isillustrated. The user device 400 may be the user devices 200 and/or 302.The user device 400 includes a chassis 402 having a display 404 and aninput device including the display 404 and a plurality of input buttons406. One of skill in the art will recognize that the user device 400 isa portable or mobile phone including a touch screen input device and aplurality of input buttons that allow the functionality discussed abovewith reference to the method 100. However, a variety of otherportable/mobile user devices and/or desktop user devices may be used inthe method 100 without departing from the scope of the presentdisclosure.

Referring now to FIG. 5, an embodiment of a computer system 500 suitablefor implementing, for example, the user device 200, the user device 302,the user device 400, the payee devices 304, and/or the payment serviceprovider device 306, is illustrated. It should be appreciated that otherdevices utilized by user, payees, and payment service providers, in thesystem discussed above may be implemented as the computer system 500 ina manner as follows.

In accordance with various embodiments of the present disclosure,computer system 500, such as a computer and/or a network server,includes a bus 502 or other communication mechanism for communicatinginformation, which interconnects subsystems and components, such as aprocessing component 504 (e.g., processor, micro-controller, digitalsignal processor (DSP), etc.), a system memory component 506 (e.g.,RAM), a static storage component 508 (e.g., ROM), a disk drive component510 (e.g., magnetic or optical), a network interface component 512(e.g., modem or Ethernet card), a display component 514 (e.g., CRT orLCD), an input component 518 (e.g., keyboard, keypad, or virtualkeyboard), a cursor control component 520 (e.g., mouse, pointer, ortrackball), a camera component 522, and/or a location sensor component523 (e.g., a Global Positioning System (GPS) device, a cell towertriangulation device, and/or a variety of other location determinationdevices known in the art.) In one implementation, the disk drivecomponent 510 may comprise a database having one or more disk drivecomponents.

In accordance with embodiments of the present disclosure, the computersystem 500 performs specific operations by the processor 504 executingone or more sequences of instructions contained in the memory component506, such as described herein with respect to the user device 200, 302,and 400, the payee device(s) 304, and/or the payment service providerdevice 306. Such instructions may be read into the system memorycomponent 506 from another computer readable medium, such as the staticstorage component 508 or the disk drive component 510. In otherembodiments, hard-wired circuitry may be used in place of or incombination with software instructions to implement the presentdisclosure.

Logic may be encoded in a computer readable medium, which may refer toany medium that participates in providing instructions to the processor504 for execution. Such a medium may take many forms, including but notlimited to, non-volatile media, volatile media, and transmission media.In one embodiment, the computer readable medium is non-transitory. Invarious implementations, non-volatile media includes optical or magneticdisks, such as the disk drive component 510, volatile media includesdynamic memory, such as the system memory component 506, andtransmission media includes coaxial cables, copper wire, and fiberoptics, including wires that comprise the bus 502. In one example,transmission media may take the form of acoustic or light waves, such asthose generated during radio wave and infrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EPROM,FLASH-EPROM, any other memory chip or cartridge, carrier wave, or anyother medium from which a computer is adapted to read. In oneembodiment, the computer readable media is non-transitory.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by the computer system 500. In various other embodiments ofthe present disclosure, a plurality of the computer systems 500 coupledby a communication link 524 to the network 308 (e.g., such as a LAN,WLAN, PTSN, and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

The computer system 500 may transmit and receive messages, data,information and instructions, including one or more programs (i.e.,application code) through the communication link 524 and the networkinterface component 512. The network interface component 512 may includean antenna, either separate or integrated, to enable transmission andreception via the communication link 524. Received program code may beexecuted by processor 504 as received and/or stored in disk drivecomponent 510 or some other non-volatile storage component forexecution.

Referring now to FIG. 6, an embodiment of a user device 600 isillustrated. In an embodiment, the user device 600 may be the userdevice 200, 302, and/or 400. The user device 600 includes acommunication engine 602 that is coupled to the network 308 and to eachof a user information form analysis engine 604 and a user informationimage analysis engine 606. The user information image analysis engine606 is coupled to a user documentation database 608. The communicationengine 602 may be software or instructions stored on a computer-readablemedium that, when executed by a processor, allows the user device 600 tosend and receive information over the network 308 and to a display onthe user device 600. For example, the communication engine 602 isoperable to send and receive the user information form over the network308, to request and receive information from the user through the userdevice 602, and/or provide a variety of other functions discussed above.The user information form analysis engine 604 may be software orinstructions stored on a computer-readable medium that, when executed bythe processor, allow the user device 600 to analyze user informationforms to determine what user information is being requested, asdiscussed above. The user information image analysis engine 606 may besoftware or instructions stored on a computer-readable medium that, whenexecuted by the processor, allow the user device 600 to analyze userinformation images to detect user information included in the userinformation images, as discussed above, and may access the userdocumentation database 608 for information that helps in that analysis,as discussed above. While the user documentation database 608 has beenillustrated as located in the user device 600, one of skill in the artwill recognize that it may be connected to the user information imageanalysis engine 606 through the network 308 without departing from thescope of the present disclosure.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the scope of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. For example, the aboveembodiments have focused on users, payment service providers, andpayees; however, a user can provide user information, or otherwiseinteract with any type of recipient, including charities andindividuals. Thus, payees as used herein can also include charities,individuals, and any other entity or person receiving user informationfrom a user. Having thus described embodiments of the presentdisclosure, persons of ordinary skill in the art will recognize thatchanges may be made in form and detail without departing from the scopeof the present disclosure. Thus, the present disclosure is limited onlyby the claims.

What is claimed is:
 1. An automated user information provision system,comprising: a non-transitory memory; and one or more hardware processorscoupled to the non-transitory memory and configured to read instructionsfrom the non-transitory memory to perform operations comprising:determining that a user device has accessed a digital user informationform that includes a first user information request section; providing,for display on the user device, a request for an image that identifies atype of document to be included in the image; receiving, from an imagecapturing device on the user device, a user information image thatincludes a document that is the type of document identified in therequest; analyzing the user information image to determine that thedocument included in the user information image includes first userinformation that is requested in the first user information requestsection; automatically filling the first user information requestsection of the digital user information form with the first userinformation that was determined to be included in the user informationimage and that is requested in the first user information requestsection; and providing, for display on a screen of the user device, thedigital user information form including the first user informationrequest section filled with the first user information.
 2. The automateduser information provision system of claim 1, wherein the non-transitorymemory and the one or more hardware processors are included in the userdevice that is provided by a mobile phone.
 3. The automated userinformation provision system of claim 1, wherein the operations furthercomprise: analyzing the digital user information form to determine thatthe first user information request section requests a type ofinformation that is provided in the type of document, wherein therequest for the image that identifies the type of document to beincluded in the image is provided in response to determining that thefirst user information request section request the type of informationthat is provided in the type of document.
 4. The automated userinformation provision system of claim 1, wherein the operations furthercomprise: receiving a user edit to the first user information that wasused to automatically fill the first user information request section ofthe digital user information form.
 5. The automated user informationprovision system of claim 1, wherein the operations further comprise:sending, to a digital user information form provider, the digital userinformation form that includes the first user information requestsection filled with the first user information.
 6. The automated userinformation provision system of claim 1, wherein the operations furthercomprise: deleting the user information image subsequent toautomatically filling the first user information request section of thedigital user information form with the first user information.
 7. Theautomated user information provision system of claim 1, wherein thedigital user information form includes at least one second userinformation request section, and wherein the operations furthercomprise: analyzing the user information image to determine that thedocument included in the user information image includes second userinformation that is requested in the at least one second userinformation request section; automatically filling the at least onesecond user information request section of the digital user informationform with the second user information that was determined to be includedin the user information image and that is requested in the at least onesecond user information request section; and providing, for display onthe screen of the user device, the digital user information formincluding the at least one second user information request sectionfilled with the second user information.
 8. A method for automated userinformation provision, comprising: determining, using at least oneprocessor, that a user device has accessed a digital user informationform that includes a first user information request section; providing,for display on a display device using the at least one processor, arequest for an image that identifies a type of document to be includedin the image; receiving, from an image capturing device on the userdevice using the at least one processor, a user information image thatincludes a document that is the type of document identified in therequest; analyzing, using the at least one processor, the userinformation image to determine that the document included in the userinformation image includes first user information that is requested inthe first user information request section; automatically filling, usingthe at least one processor, the first user information request sectionof the digital user information form with the first user informationthat was determined to be included in the user information image andthat is requested in the first user information request section; andproviding, for display on the display device of the user device usingthe at least one processor, the digital user information form includingthe first user information request section filled with the first userinformation.
 9. The method of claim 8, wherein the at least oneprocessor is included in the user device that is provided by a mobilephone.
 10. The method of claim 8, further comprising: analyzing, usingthe at least one processor, the digital user information form todetermine that the first user information request section requests atype of information that is provided in the type of document, whereinthe request for the image that identifies the type of document to beincluded in the image is provided in response to determining that thefirst user information request section request the type of informationthat is provided in the type of document.
 11. The method of claim 8,further comprising: receiving, using the at least one processor, a useredit to the first user information that was used to automatically fillthe first user information request section of the digital userinformation form.
 12. The method of claim 8, further comprising:sending, to a digital user information form provider using the at leastone processor, the digital user information form that includes the firstuser information request section filled with the first user information.13. The method of claim 8, further comprising: deleting, using the atleast one processor, the user information image subsequent toautomatically filling the first user information request section of thedigital user information form with the first user information.
 14. Themethod of claim 8, wherein the digital user information form includes atleast one second user information request section, and wherein themethod further comprises: analyzing, using the at least one processor,the user information image to determine that the document included inthe user information image includes second user information that isrequested in the at least one second user information request section;automatically filling, using the at least one processor, the at leastone second user information request section of the digital userinformation form with the second user information that was determined tobe included in the user information image and that is requested in theat least one second user information request section; and providing, fordisplay on the display device using the at least one processor, thedigital user information form including the at least one second userinformation request section filled with the second user information. 15.A non-transitory machine-readable medium having stored thereonmachine-readable instructions executable to cause at least one processorto perform operations comprising: determining that a user device hasaccessed a digital user information form that includes a first userinformation request section; providing, for display on the user device,a request for an image that identifies a type of document to be includedin the image; receiving, from an image capturing device on the userdevice, a user information image that includes a document that is thetype of document identified in the request; analyzing the userinformation image to determine that the document included in the userinformation image includes first user information that is requested inthe first user information request section; automatically filling thefirst user information request section of the digital user informationform with the first user information that was determined to be includedin the user information image and that is requested in the first userinformation request section; and providing, for display on a screen ofthe user device, the digital user information form including the firstuser information request section filled with the first user information.16. The non-transitory machine-readable medium of claim 15, wherein theoperations further comprise: analyzing the digital user information formto determine that the first user information request section requests atype of information that is provided in the type of document, whereinthe request for the image that identifies the type of document to beincluded in the image is provided in response to determining that thefirst user information request section request the type of informationthat is provided in the type of document.
 17. The non-transitorymachine-readable medium of claim 15, wherein the operations furthercomprise: receiving a user edit to the first user information that wasused to automatically fill the first user information request section ofthe digital user information form.
 18. The non-transitorymachine-readable medium of claim 15, the operations further comprise:sending, to a digital user information form provider, the digital userinformation form that includes the first user information requestsection filled with the first user information.
 19. The non-transitorymachine-readable medium of claim 15, wherein the operations furthercomprise: deleting the user information image subsequent toautomatically filling the first user information request section of thedigital user information form with the first user information.
 20. Thenon-transitory machine-readable medium of claim 15, wherein the digitaluser information form includes at least one second user informationrequest section, and wherein the operations further comprise: analyzingthe user information image to determine that the document included inthe user information image includes second user information that isrequested in the at least one second user information request section;automatically filling the at least one second user information requestsection of the digital user information form with the second userinformation that was determined to be included in the user informationimage and that is requested in the at least one second user informationrequest section; and providing, for display on the screen of the userdevice, the digital user information form including the at least onesecond user information request section filled with the second userinformation.